Eikre wrote:Okay, so your argument really isn't that I'm incorrect, it's just that I'm whiny, and that Virgil is also an idiot because he started a discussion about a novel idiosyncrasy?
No, my argument is that you are completely full of shit and every single thing you said in this post:
Eikre wrote:This is a really irritating adjudication, because the rules almost have your expectations covered. Either emergently or explicitly, they dis-include all of the weapons that don't threaten from being used to make an AoO. Ranged weapons don't threaten, and explicitly can't be used to make an AoO. An uncast spell doesn't threaten, but you can't cast a spell except as a discrete action. A weapon that isn't threatening because of inappropriate reach (like a lance, when you're threatening with armor spikes, or visa-versa) can't be used, because... it just can't be used to make the attack against a person at that distance at all. And an untrained fist-fighter, who doesn't threaten, is ordinarily covered by a rule in the Combat section of the PHB, under the list of standard actions, which says: "An unarmed character can’t take attacks of opportunity."
That last rule fails to cover the edge case you've presented, which is that, factually, a person who is not unarmed can still make an unarmed strike. That said, it's still a pretty clear mandate to preclude someone from engaging in your bring-a-fist-to-a-knife-fight strategy, and there's even a tortured interpretation that, in the moment you make an unarmed strike, you are operating as an unarmed combatant.
Here's my real outlook, though: The rules are incredibly fucking inelegant and the editors should be ashamed of themselves. They separately define the list of "weapons that threaten" and "weapons that can't be used for an AoO," with the apparent intention that the second list be an exhaustive inverse of the first. That's horseshit! Write one list, and a direct correlation in place of the second! "You can only make an attack of opportunity using a weapon you threaten with." There, I fixed it, it took me literally two seconds to come up with, and I didn't have to scatter a half-dozen piecemeal mechanics over as many nonconsecutive pages to make it work. Set theory, motherfuckers!
is both wrong and stupid.
And that Virgil asked a question to which the answer is "Yes. And the rules expressly state that, so who fucking cares, this isn't an idiosyncrasy."
Eikre wrote:your oversight was the product of a ruleset that, while actually very good and complete, could still do with another editorial once-over.
It was a product of the layout on the SRD, if that table was two pages up right next to the other one, or in the other section, the one labeled "special attacks", then no one would miss it.
Eikre wrote:Is this a trifling difference? Yeah, of fucking course it is. Literally everyone is capable of eliding the difference and having a perfectly good time playing the game. I know! Our little shitfit here has not been revelatory, in this regard. But my interest is in the illustration of how connoting the rules isn't the same as actually writing them down, and the reason I care is because I think that the practiced eye which identifies these quibbling little idiosyncrasies is also the rigor which prevents a prospective developer from making their own compositional errors. The results end up being better in action and easier to learn, and presumably that's something we care about, around here.
Look you fucking idiot, you aren't the one true game designer looking into this. Your position is basically nonsense from step one because you believe that the rules that explicitly stated you can fucking grapple as AoO really meant to only let you grapple with all those grappling weapons.
Guess what, the special actions in the Tomes have the exact same fucking language, but they have it written in the actual header for the actions, instead of in a table, no one would miss it, and it is on the same page with the special actions.